chore: enable npm publication bootstrap for 0.2.0#5
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a3fcda2af9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "description": "Kernel CLI: a repo-local quality system and portable operating layer for coding agents.", | ||
| "type": "module", | ||
| "private": true, | ||
| "license": "Apache-2.0", |
There was a problem hiding this comment.
In the npm-release workflow I inspected, the job runs pnpm test before the publish gate (.github/workflows/npm-release.yml), and tests/release-readiness.test.ts:169 still asserts packageJson.private is true. With private removed here, the release job and CI test step fail before reaching npm publish, so the 0.2.0 publication bootstrap cannot complete until the readiness test/checklist are updated for the non-private release state.
Useful? React with 👍 / 👎.
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
1 participant
Removes package.json private:true on public main only. Required before npm-release workflow can publish @mattbaconz/kernel@0.2.0.
Made with Cursor